Skip to content

[bulk] Add release-plan.yaml (2026-02-23-001)#62

Merged
eric-murray merged 1 commit intomainfrom
bulk/release-plan-rollout-22305485219
Apr 2, 2026
Merged

[bulk] Add release-plan.yaml (2026-02-23-001)#62
eric-murray merged 1 commit intomainfrom
bulk/release-plan-rollout-22305485219

Conversation

@hdamker-bot
Copy link
Copy Markdown
Contributor

@hdamker-bot hdamker-bot commented Feb 23, 2026

Add release-plan.yaml for automated release tracking

TL;DR: This PR adds release-plan.yaml for automated release tracking (replacing manual API Release Tracker pages on wiki).

Note: Adding release-plan.yaml is a prerequisite for the upcoming release automation process.
This PR does not yet enable the automated release workflow; onboarding will follow separately.

What is this?

The release-plan.yaml file declares your release plan for this repository and its APIs. It enables:

  • Automated release tracking (replacing manual API Release Tracker pages on wiki)
  • CI validation of release readiness
  • Automated release preparation (enabled during onboarding)

Pre-populated data

The release-plan.yaml file is generated from your current release data and repository settings:

  • Release tag: target_release_tag is set to r2.2 (detected from your current release)
  • APIs: derived from your current release (r2.2)
  • Contacts: from your CODEOWNERS file

👉 Please review and adjust if API-specific contacts differ from repository-wide codeowners.

What to do next

Option A: Merge as-is (if no release planned yet)

  • The file reflects your current release state (r2.2, Fall25)
  • target_release_type: none means "no release currently planned"
  • Just merge

Option B: Update before merging (if planning your next release now)

  1. Set target_release_type (e.g. pre-release-alpha or pre-release-rc)
  2. Update target_release_tag for your next release:
    • New cycle: increment first number, reset second to 1 (e.g., r3.2 → r4.1)
    • Progression in same cycle: increment second number (e.g., r3.2 → r3.3)
  3. Update target_api_version for any APIs being changed
  4. Optionally add meta_release: Sync26 if participating in the meta-release
API status and release type meanings (for later)

target_api_status

Status Meaning
draft API work in progress / definition not ready
alpha API definition exists, ready for early feedback
rc Release candidate, feature-complete
public Public release

target_release_type

Value When to use
none No release currently planned
pre-release-alpha Early, incomplete preview release for feedback
pre-release-rc Release candidate publication
public-release Public CAMARA release
maintenance-release Patch/maintenance release in an existing cycle

Documentation

📖 Release Management Documentation
📖 The release-plan.yaml File
📖 Release Lifecycle
📖 API Versioning

@hdamker-bot hdamker-bot added the automated Automated bulk operations from project-administration label Feb 23, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Feb 23, 2026

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.0s
✅ API spectral 1 0 1.44s
✅ GHERKIN gherkin-lint 1 0 0.34s
✅ REPOSITORY git_diff yes no 0.0s
✅ REPOSITORY secretlint yes no 0.58s
✅ YAML yamllint 1 0 0.36s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

@GillesInnov35
Copy link
Copy Markdown
Contributor

GillesInnov35 commented Feb 23, 2026

@hdamker-bot

repository:
meta_release: Fall25

could you tell me what the concerned meta-release. Is it the current one or for example spring26 even if no new release has been planed ?

Thanks
Gilles

@hdamker
Copy link
Copy Markdown
Contributor

hdamker commented Feb 23, 2026

@hdamker-bot

repository: meta_release: Fall25

could you tell me what the concerned meta-release. Is it the current one or for example spring26 even if no new release has been planed ?

Thanks Gilles

@GillesInnov35 next reachable meta-release is Sync26 (aka Fall26). Spring26 is mainly for Commonalities and ICM.

@GillesInnov35
Copy link
Copy Markdown
Contributor

GillesInnov35 commented Feb 24, 2026

thanks @hdamker-bot , yes I know that spring26 concerns only Commonalities and ICM. My question was not clear, sorry. It concerns the sentence # How this repository participates in CAMARA releases
My question is: as this API has not been concerned by the next meta-release spring26, should we write in the block
repository:
meta_release: Fall26 or let meta_release: Fall25

@hdamker
Copy link
Copy Markdown
Contributor

hdamker commented Feb 24, 2026

thanks @hdamker-bot , yes I know that spring26 concerns only Commonalities and ICM. My question was not clear, sorry. It concerns the sentence # How this repository participates in CAMARA releases My question is: as this API has not been concerned by the next meta-release spring26, should we write in the block repository: meta_release: Fall26 or let meta_release: Fall25

If the plan of the team is to participate with their next public release in Sync(Fall)26 (which I hope), change it to Sync26. If you want to do a release already earlier, change the release track to independent (an initial API can release at any time if needed).

@GillesInnov35
Copy link
Copy Markdown
Contributor

GillesInnov35 commented Feb 24, 2026

thanks, that's clear

@hdamker hdamker mentioned this pull request Feb 24, 2026
Closed
16 tasks
@hdamker
Copy link
Copy Markdown
Contributor

hdamker commented Apr 2, 2026 •
edited
Loading

Gentle reminder: this PR adds the release-plan.yaml configuration file as part of the release automation onboarding for CAMARA repositories (see ReleaseManagement#379). The file is purely additive and does not change any existing code or API definitions. A codeowner approval is needed to merge it. cc @eric-murray @GillesInnov35 @grgpapadopoulos @fernandopradocabrillo

GillesInnov35
GillesInnov35 approved these changes Apr 2, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@GillesInnov35 GillesInnov35 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@eric-murray eric-murray merged commit cdedf52 into main Apr 2, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@eric-murray eric-murray eric-murray approved these changes

@GillesInnov35 GillesInnov35 GillesInnov35 approved these changes

@grgpapadopoulos grgpapadopoulos Awaiting requested review from grgpapadopoulos grgpapadopoulos is a code owner

@fernandopradocabrillo fernandopradocabrillo Awaiting requested review from fernandopradocabrillo fernandopradocabrillo is a code owner

Assignees

No one assigned

Labels

automated Automated bulk operations from project-administration

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@hdamker-bot @GillesInnov35 @hdamker @eric-murray